Repository navigation
chore(release): v0.2.1 - #132
Merged
Merged
Conversation
Brings the 0.2.0 version bump (package.json, template/package.json, lockfiles, CHANGELOG) back into develop so the next feature work starts from the released version. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
## Summary Back-merges the v0.2.0 version bump commit (`2415393`) from `main` (PR #128) into `develop`. Step 10 of the release procedure (CLAUDE.md → Release procedure): > Back-merge to develop so the version bump and any release-only fixes don't get lost. The original `release/v0.2.0` branch was auto-deleted by GitHub on merge into `main`, so this PR reuses a `chore/back-merge-v0.2.0` branch with the same merge state. ## Why `release/v0.2.0` was merged into `main` via PR #128 with `--merge` (commit `ea21d01`). The version bump commit `2415393` is now only on `main`; without this back-merge, the next feature work on `develop` would start from `0.1.13` again. ## Test plan - [ ] Diff shows only `package.json` x2, lockfiles x2, and `CHANGELOG.md` (`+47 / -0` from the `[0.2.0]` entry). - [ ] After merge, `develop` HEAD reports `version: 0.2.0` in both `package.json` and `template/package.json`. - [ ] CI smoke matrix green on `develop` post-merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
- Replace ghost variant with secondary on CLI error Retry button so it has a visible border and background against the danger banner - Add RotateCcw icon to the Retry button for clear affordance - Replace unicode ▴/▾ characters in Timeline toggle with ChevronUp / ChevronDown from @lucide/svelte for consistent pixel-grid alignment Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…le (#130) ## Summary - Replace `ghost` variant with `secondary` on the CLI error Retry button — adds visible border + background against the danger banner - Add `RotateCcw` icon to the Retry button for clear affordance - Replace unicode `▴`/`▾` characters in Timeline toggle with `ChevronUp` / `ChevronDown` from `@lucide/svelte` for consistent pixel-grid alignment ## Why Ghost variant blended into the alert background making retry look like plain text. Unicode arrows have inconsistent sizing vs lucide icons used elsewhere in the UI. ## Test plan - [ ] Trigger a CLI error (stop forgeplan binary), verify Retry button shows with border/icon - [ ] Click Retry — pollers refresh - [ ] Timeline toggle shows ChevronDown when expanded, ChevronUp when collapsed - [ ] Both light and dark themes look correct 🤖 Generated with [Claude Code](https://claude.com/claude-code)
…bobox variant
bin/commands/start.mjs: Replace heartbeat(id) with register({...entry,
heartbeatAt}) in the interval so a lost registry row (concurrent write race,
ADR-004 §5) is automatically re-added within 30 s instead of staying gone
forever. Extract instanceEntry once; heartbeat ticks spread it.
bin/lib/registry.mjs: Add TODO on heartbeat() silent-skip-if-missing gap;
fix stale "Heartbeat reconciles" comment in deregister().
template/src/shared/ui/combobox: Add ghost variant — transparent chrome that
blends into the header bar. Change icon from ChevronDown to ChevronsUpDown
(no rotation on open; bidirectional icon fits a select control better).
Add ghost-sm + ghost-md entries to playground showcase (rule 24).
template/src/entities/instance/api/store.ts: Reduce instance poll interval
3 s (was 5 s) for faster new-instance detection in the switcher combobox.
template/src/widgets/health-bar/ui/HealthBar.svelte: Use ghost variant for
the instance switcher so it blends into the monospace header.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…isible instance switcher with empty state Ghost variant hover/open now uses color-mix(in srgb, var(--fg) 10%, transparent) instead of var(--bg-1), giving a theme-adaptive subtle overlay (works in both dark and light themes) with no visible border. HealthBar always renders the instance combobox; when only one instance is running the dropdown shows an empty state explaining what the switcher does and how to start a second instance. Refs: PRD-027
…the dropdown bits-ui Combobox requires ComboboxInput to be in the DOM to register with the listbox context — without it clicking the Trigger does nothing. In the no-other-instances branch we now always mount the input but collapse it (visibility:hidden + height:0) so it takes no space and is not exposed to AT. Refs: PRD-027
bits-ui Combobox anchors its floating Content to the ComboboxInput via
FloatingLayer.Anchor. When Input is inside the Content (our pattern),
the floating layer sees a circular reference and mis-positions the popup
(Y=-253, off-screen).
Fix: pass customAnchor={switcherEl} to ComboboxContent which forwards it
to ComboboxPrimitive.Content (via restProps → PopperLayer). This tells
bits-ui's floating-ui to use the .project-switcher div as the reference
element instead of the Input, giving correct below-trigger positioning.
With the anchor fixed, ComboboxInput is only rendered when hasOtherInstances
(needed for search); the empty state branch has no Input at all and shows
a plain explanation div instead.
Refs: PRD-027
Replaces bits-ui Combobox with Popover.Root+Portal+Command.Root so the floating layer correctly escapes the header's backdrop-filter stacking context. Previous implementation anchored to ComboboxInput (the FloatingLayer.Anchor inside the portal), causing off-screen positioning and rendering behind the graph toolbar. Key changes: - Popover.Portal ensures content renders at body level (z-index clean) - Command.Empty auto-shows empty state when no instances listed - Command.Item with keywords for search filtering - Ghost trigger button styled via scoped .project-switcher :global() selectors — hover uses color-mix(in srgb, var(--fg) 10%, transparent) for adaptive semi-transparent overlay across all themes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
## Summary
- Rewrites the instance switcher from `Combobox` to `Popover.Root` +
`Popover.Portal` + `Command.Root` (shadcn-svelte pattern)
- Fixes empty state not showing: `Popover.Portal` escapes the header's
`backdrop-filter` stacking context, which was trapping the floating
layer inside the header
- Fixes off-screen positioning: previous Combobox anchored content to
`ComboboxInput` (the `FloatingLayer.Anchor`), causing broken positioning
when the input was hidden or absent
- Ghost trigger button hover uses `color-mix(in srgb, var(--fg) 10%,
transparent)` — adapts to light/dark/orch themes without border
- `Command.Empty` auto-renders the empty state when no instances are
listed (no manual `{:else}` needed)
- `Command.Item` with `keywords` prop enables search by project name,
host, and port
- Fixes multi-instance registration: heartbeat now re-registers lost
entries to survive concurrent write races
- Adds `ghost` combobox variant with semi-transparent hover/open states
## Why
Instances were spawning on different ports but the switcher showed
nothing — the registry registrations were silently lost in
concurrent-write races, and the dropdown positioned off-screen at Y=-253
due to the circular floating anchor dependency.
## Test plan
- [ ] Open forgeplan-web, click the project name in the header — empty
state shows "Instance switcher / Only one instance is running..."
- [ ] Start a second instance (`npx @forgeplan/web start` in another
project) — switcher shows both with search input
- [ ] Hover on trigger: semi-transparent bg in light, dark, orch themes;
no border
- [ ] Clicking an item navigates to that instance's URL
🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fixcommits fromdevelopsince v0.2.0Why
All changes are bug fixes for features shipped in 0.2.0 (instance switcher, registry heartbeat, UI regressions).
Test plan
npm run smokepasses locally againstdist/anddist-nightly/--merge(no squash)v0.2.1onmain→ GitHub Release → npm publish via CIrelease/v0.2.1intodevelop🤖 Generated with Claude Code